$webwork.htmlEncode($page.space.name) : 6- Advanced GeoServer Features
This page last changed on Sep 08, 2006 by bowens.
STEP 6: Advanced GeoServer FeaturesCaching - Tiling your Mapping ClientGeoServer supports caching of requests. This is very useful if you have a tiled WMS client, such as Open Layers. Tiling is what you see on Google Maps. To use caching, you need to do two things. First is put a program called Squid to listen on a certain port. Squid will cache all requests that are directed to the port it is listening on. Second, you need to tell GeoServer to modify the headers on the request results. This is done in the FeatureType editor.
By default, GeoServer sets the header timeout time of all request results to end immediately. This is so many web map clients will get a new result each time they request something from geoserver. But when you enable caching, the header won't be set to expire for a while, so all other requests just return the result without having to be processed. This makes things very fast. SLD Post and Inline FeaturesIs there an SLD you would like to use that isn't on the server you are retrieving the map from? No problem! With GeoServer you can send an SLD document along with your GetMap Request. With this you can also send your own features to be rendered along with the map. These are called Inline Features. Learn how to do both with this tutorial: GeoServer's KML/KMZ OutputGeoServer has a fairly advanced KML/KMZ rendering system that fully supports SLD (up to what Google Earth can handle). This tutorial describes in detail how you can limit the features returned, return features back as a raster image instead of XML, and how to turn attribution on and off: NASA World WIndIf you have World Wind installed, you can follow this tutorial on how to serve data from GeoServer to it: GeoServer Tutorial Pagehttp://docs.codehaus.org/display/GEOSDOC/Documentation+Tree
4-nav_welcome_to_ft.jpg (image/jpeg)
|
Document generated by Confluence on Jan 16, 2008 23:27 |